Why oh why didn't I look at open PRs prior to opening #129...

Thanks for this @ikatyang, looks much better than my quick-and-dirty version!

Actually, does this support glob-ing too? Like tslint-config-prettier-check ./**/tslint.yml?

It's based on your shell:

$ node -e "console.log(process.argv)" ./fixtures/tslint.*.json
[ '/usr/local/Cellar/node/9.10.1/bin/node',
  './fixtures/tslint.all.json',
  './fixtures/tslint.empty.json',
  './fixtures/tslint.error.json',
  './fixtures/tslint.false.json' ]

And also you can try it with this PR:

git clone https://github.com/alexjoverm/tslint-config-prettier --branch feat/check-multiplie-config-files
cd tslint-config-prettier
npm install
node bin/check.js ./fixtures/tslint.*.json

And the reason why I don't want to use some node-glob-like dependency is that this package is mainly just a config file, that kind of dependency is somehow too heavy for us, a simple tool should be enough.

glob@7.1.2
├── fs.realpath@1.0.0
├─┬ inflight@1.0.6
│ ├── once@1.4.0 deduped
│ └── wrappy@1.0.2
├── inherits@2.0.3
├─┬ minimatch@3.0.4
│ └─┬ brace-expansion@1.1.11
│   ├── balanced-match@1.0.0
│   └── concat-map@0.0.1
├─┬ once@1.4.0
│ └── wrappy@1.0.2 deduped
└── path-is-absolute@1.0.1

Yeah my question was stupid, of course it support globbing if you can pass it multiple files, duh.

And the reason why I don't want to use some node-glob-like dependency is that this package is mainly just a config file, that kind of dependency is somehow too heavy for us, a simple tool should be enough.

I totally understand that, I had the exact same reasoning when opening #129.

Props to you for taking this up! Can't wait to simplify my yarn script :)